Comments
-
Got it, thanks, and you're right, ARP Bridging was already enabled. I also added a static entry in the ARP table for the LAN host I was pinging from but that didn't help. When I checked the box to Publish Entry, it changed the MAC address to the X0 interface address, and wouldn't allow me to change that, so I left Publish…
-
No bridges. I looked at the L2 bridge for X2 but since it wipes out the static IP I didn't see how the static route to the Company B firewall would function.
-
Thanks again for your reply—it's taken me a while to get access to the network again. I changed the default gateway on the X2 interface to 192.168.99.2 (the other company's firewall) and now the dropped ARP requests from the other firewall (in response to pings from our LAN host) show our LAN host as the destination IP—so…
-
Thanks for your response, Tony. I finally got a chance to export the log and got detail on one of the dropped ARP requests. I have pasted it below my message here. A couple of clues: 1: 'ARP bridge not supported' Not sure what to make of this. 2: 'Target IP address: 10.10.18.254'. I don't understand how that came up as the…
-
Hello Mustafa, I still haven't resolved this. I did a new packet capture, and this time filtered to include source of 192.168.99.2 (Company B X2 interface) or 192.168.50.200 (Company B printer, the ping target). See attachment. It shows that 192.168.99.2 is replying with ARP requests that are being dropped by Company A's…
-
Sorry for the long delay. Company B's packet sniffer saw my (Company A) LAN host's pings to their printer, but no reply. They weren't able to identify a reason on their end why our firewall's X2 interface gets a reply from their printer but our LAN host does not. From their side, they were able to ping our LAN host from…
-
Thanks. Screenshot of the packet capture attached, detail copied below. 10.10.18.5 is the host on Company-A's LAN, 192.168.50.200 is the printer. It looks like it's forwarding out the X2 interface as desired? Ethernet Header Ether Type: IP(0x800), Src=[68:5b:35:c2:4c:f4], Dst=[18:b1:69:f3:c6:c0] IP Packet Header IP Type:…
-
Thanks, MustafaA. I removed the access rule as superfluous since X0, X2 and the address objects for the Company B firewall interface and printer are all in the LAN zone. The printer responds to pings from Company A's firewall, so it looks like the static route is working. However, I still can't ping the printer from a…
-
Hello MustafaA, I have tried to set up the configuration you suggest, but Company B's printer is still not accessible from Company A's LAN (doesn't respond to pings or attempts to configure a print queue). It may be that Company B didn't configure their interface or access rules as requested, but can you please check my X2…
-
Thank you very much for the clear answer, MustafaA! Working from the diagram you sent, would it also be possible to configure Company A's X2 interface for connecting directly to the LAN switch of Company B? If so, how do you recommend to configure that X2 interface? Would other settings be needed on Company A's router?…
-
Thanks for the reply, MustafaA, sorry for the slow follow-up. I hope my sketch is readable. The two companies have separate networks and firewalls that are housed on the same network rack. Maybe what I'm trying won't work but I saw it suggested on another forum. I control Company B's setup, not Company A, but they would…
-
I'm trying to do the same: print from computers on subnet A (interface X0) to a printer on subnet B. Subnet B is managed by a separate router. Here's what I plan to do: Assign interface X2 a static IP on subnet B and connect it to subnet B's LAN switch. Create an address object with printer's subnet B IP address. Create a…